README.DOC for InterChange Version 1.1
Last Updated 01/23/95
INTRODUCTION
This file, README.DOC, serves to present information about the
product which is not reflected in the InterChange manual. This
includes documentation errors, additions, and clarifications.
PLEASE TAKE THE TIME NOW TO READ THROUGH THIS FILE, or do so at
your earliest convenience.
SOFTWARE MODS
Even the best software has bugs when it is as complex as InterChange.
In order to keep your software current, eSoft distributes a program
update system to fix any bugs which we find in the software. You
can use this system to protect your software investment. Each fix
(called a mod) is assigned a number. This release includes all mods
up to and including:
┌───┐
│ 0 │ <--- MOD LEVEL OF THE SOFTWARE ON THESE DISKETTES
└───┘
The software update program (UPDATE.EXE) is on this diskette. The
latest software update data file (UPDATE.BIN) is always available at
no charge for download from the eSoft, Inc. Support Board (for access
information, see Chapter 12 of your TBBS manual). If you are
experiencing difficulty with the software, obtain and apply all newer
mods before taking any other action.
LAST MINUTE ADDITIONS AND CORRECTIONS TO YOUR INTERCHANGE MANUAL
Script language enhancements
----------------------------
Enhancements have been made to the InterChange Script language as follows:
1. Command to read a text parameter into a string variable:
SCAN Sn <time> [GOTO] <label>
Beginning with the first non-blank character received after the SCAN
is issued, a parameter is scanned from the received data into the
specified string variable until either a blank, end-of-line, comma,
or semi-colon is encountered. If <time> is specified, then the scan must
complete in the time specified (40 seconds is default if <time> not
specified). <label> is where script will transfer if the scan times out
(default is to abort the script if <label> is not present and the SCAN
times out).
Note: All WHEN conditions are honored during a SCAN, and will not affect
the scanning of the data into the variable. A maximum of 80 characters
are allowed on a scanned variable, and the scan will terminate at that
point if no delimiter has been encountered.
2. IF PORT command:
IF [NOT] PORT [GOTO] <label>
This command will test to see if a serial port is currently attached to
this session. A serial port may be attached either because a GRAB has
occurred, or because this session is taking place as a ghost task on a
line which has a port (i.e. not a ghost line).
3. On IF commands, NO is now synonymous with NOT. This allows some IF
commands to "read better" such as:
IF NO CARRIER GOTO <label>
4. ERASE command:
ERASE <filespec>
This command will delete files from the local disk. <filespec> must be a
fully qualified file specification with a drive and path specified. Wild
cards are allowed.
Examples:
ERASE C:\TBBS\TEXT\DOC1.TXT
Will erase the single file DOC1.TXT
ERASE C:\TBBS\TEMP\*.*
Will erase all files in the directory C:\TBBS\TEMP
Note: No error results if the file(s) to be erased do not exist.
5. RETURN parameter command:
RETURN Rn [= <string>]
For TBBS 2.3, returns the string value to the TBBS return parameters
R1 through R9 selected. Maximum string length=80 characters, and the
total TBBS length for all return parameters is 256 characters.
Note: If <string> is absent, the specified return parameter will be
reset to a null value.
Note: In TBBS 2.2, this script command does nothing. It does
not cause an error.
6. FORMAT command:
FORMAT 8N1|7E1
This command sets the slave line's parity for script operations.
7. Additional "Raw" ASCII SEND protocol:
SEND RASCII <filespec>
The RASCII protocol has been added. It operates the same as a
SEND ASCII, except that it sends all characters in the file exactly
as present up to either a ^Z or EOF mark. The primary difference
from ASCII is that is also sends the <LF> characters after the <CR>
instead of only the <CR> as ASCII does.
8. DOTBBS command:
DOTBBS [TYPE] <num> [OPTDATA] [<string>]
Example: DOTBBS TYPE 1 OPTDATA "C:\TEXT\FILE1.TXT /D"
Note: DOTBBS always runs on the MASTER line, so any downloads will
go to the MASTER line, not the slave, in data switch mode with a line
attached.
9. SEND command allowed in data switch mode:
The SEND command is now allowed in data switch mode and will
ALWAYS send to the SLAVE line. Thus you can now control downloads from
the TBBS machine to either the master or slave line in a data switch
configuration using a script.